Skip to content

ci: run Security Updates weekly instead of daily - #98

Closed
albertotb wants to merge 1 commit into
mainfrom
chore/security-updates-weekly
Closed

ci: run Security Updates weekly instead of daily#98
albertotb wants to merge 1 commit into
mainfrom
chore/security-updates-weekly

Conversation

@albertotb

Copy link
Copy Markdown
Member

Restores .github/workflows/security-updates.yml to cron: "37 3 * * 1" (Mondays 03:37 UTC), from cron: "30 3 * * *" (daily 03:30 UTC).

  • The weekly schedule was merged here on 2026-07-31, then overwritten back to daily by sync: update from python-copier-template (sync: update from python-copier-template #94). August billing shows 23 runs instead of 5.
  • The Security Updates job finishes in well under a minute but is billed a full minute per run, so a daily schedule is almost entirely rounding overhead.
  • The :37 offset is deliberate: GitHub delays scheduled workflows that pile onto the :00/:30 marks.

The root cause is upstream: python-copier-template still shipped the daily cron, so every copier update re-reverted this file. That is fixed in Komorebi-AI/python-copier-template#44, which stops the daily schedule re-propagating on every copier update. This PR is the local re-fix; merge the template PR too, otherwise the next sync reverts it again.

Only the cron line changed.

Restores the weekly schedule, which was overwritten back to daily by
'sync: update from python-copier-template' (#94).

The job finishes in well under a minute but is billed a full minute per
run, so a daily schedule is almost entirely rounding overhead.
@albertotb

Copy link
Copy Markdown
Member Author

Closing without merging: the fix belongs upstream in python-copier-template (Komorebi-AI/python-copier-template#44). Once that merges, the weekly cron propagates here via the normal template sync, so this PR would be redundant and would conflict with the sync.

@albertotb albertotb closed this Sep 1, 2026
@albertotb
albertotb deleted the chore/security-updates-weekly branch September 1, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant